@littlematch0123 First, thanks for much for the contribution, I really appreciate it! Second, can you briefly let me know the process/flow that was in-place when you caught this error? Specifically, were you working off of a forked repo? This says something about it being an issue with forks, but it's still new to me (I haven't tried running this in a while, though). I have no problem forcing the write permission since it's an action, just want to try to document it, thanks!

Thanks for your response. This below is the "Post comment" part in your action.

    - name: Post comment
      uses: mshick/add-pr-comment@v1
      if: ${{ steps.write-good.outputs.result }}
      with:
        message: |
          ${{ steps.write-good.outputs.result }}
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        repo-token-user-login: 'github-actions[bot]' # The user.login for temporary GitHub tokens
        allow-repeats: false # This is the default

You use the "mshick/add-pr-comment" action to add a comment to a pull request's issue. Note that "mshick/add-pr-comment" action need the write access
https://github.com/mshick/add-pr-comment#usage

So, that's the reason for adding the "pull-request: write" permission

I'm an English learner, I'm not sure if what I said above is polite.
Please bear with me.

@littlematch0123 It was very polite and detailed, thank you for the info! I'll merge and issue a new release. Thanks again!

@littlematch0123 Sorry for the delay, and thanks again! Release 1.6